You will need a GitHub account for this course.

Join class Wiki and list your name in lastName alphabetical order hyperlinked to your GitHub account.

Git Workflows

Git-Github Exercise

OO Analysis and Design

Form Teams

Team Meetings

Install and explore ArgoUML.

Learn Git

Git videos (short):
What is VC,
What is Git,
Start Git,
Win with Git

Unit Testing Checklist

TP1: In Class: Team Intro

Email team details of Team name, names, emails, github accounts to bowringj@cofc.edu SUBJECT = "CSCI360GitHub".

I will create teams and team repositories and each of you will receive an invite.

TP2 Description: Analyze and Design Software to control a Dual-Alarm AM/FM Clock Radio

UP Inception

Evolutionary Requirements

Use Cases

Chp 4, 5
Architecture as Hallucination

Unmasking Ethical Risks

HW1: 2+-page response that compares and contrasts Booch with Gotterbarn/Miller:

Submit here.

Ancient Greek Computer

HW2: Identify and write in "casual format" at least 5 use cases for a simple answering machine.

Submit here.

Grady Booch Podcasts

Use Case

Team Reports

UP Elaboration I

NOTE:

PDFs or other GitHub supported formats ONLY

TP2 Deliverable 1: Inception Documents: Vision, Use-Case enumeration with 2 use cases "fully dressed", supplemental specs, glossary

Submit in team repo.

HW3: Create a domain model (see 9.4 in text) for simple answering machine from HW2.

Submit here.

Team Reports

System Sequence Diagrams

Agile Domain Modeling Example

Sequence Diagrams

TP2 Deliverable 2: Elaboration I Documents: all uses cases fully dressed and domain model.

Submit in team repo.

HW4: Create system sequence diagrams and operation contracts for simple answering machine.

Submit here.

Team Reports

Logical Architecture

TP2 Deliverable 3: Elaboration I Documents: System Sequence diagrams and operation contracts.

Submit in team repo.

Object Design

UML Interaction Diagrams

TP2 Deliverable: Revise D3 per lessons learned and comments;

Submit in team repo.

HW5: Patterns

Submit here.

What the Doormouse Said

Whole Earth Catalog and Stewart Brand

TP2 Deliverable 4: Explore your :System object (application layer) and identify objects needed to implement your operations; Suggest object responsibilities and collaborations with example sequence diagrams;

Submit in team repo.

Team Reports

Review

TP2 Deliverable 5: Complete the realization of your defined contracts with detailed sequence diagrams derived from your analysis of object responsibilities and collaborations; Keep in mind GRASP, especially Information Expert, Creator, Controller, and Low Coupling;

Submit in team repo.

Designing for Visibility

Mapping Designs to Code

HW6: Simple answering machine: complete the realization of your defined contracts with detailed sequence diagrams derived from your analysis of object responsibilities and collaborations; Keep in mind GRASP, especially Information Expert, Creator, Controller, and Low Coupling;

Submit here.

TP2 Deliverable Revise D5: Revise D5 per lessons learned and comments;

Submit in team repo.

R 08 Mar

TP2 Deliverable 6: Produce Java classes to implement your design as specified in your sequence diagrams; use NetBeans to create project [teamnameAlarmClock] (no spaces) with Junit 4.0 tests; use test-driven development by first creating tests for each class and method; use package structure com.csci360.alarmclock;

Submit in team repo.

HW7: Simple answering machine: Produce Java classes to implement your design as specified in your sequence diagrams; use NetBeans to create project [lastFirstAnserwingMachine] (no spaces) with Junit 4.0 tests; use test-driven development by first creating tests for each class and method; use package structure com.csci360.answeringMachine;

Submit here.

TP2 Deliverable: Revise D6 per comments;

Submit in team repo.

HW8: Produce activity diagrams for:

1) modeling the process of buying groceries, starting with a shopping list;

2) the binary search algorithm;

Submit here.

TP2 Deliverable 7: Produce state machine models of the UI for the alarm clock based on your previously defined system operations;

Submit in team repo.

HW9: Produce state machine models of the UI for the answering machine based on your previously defined system operations;

Submit here.

TP2 Deliverable: REVISE D7;

Submit in team repo.

TP2 Deliverable 8: Implement GUI within the package structure for the alarm clock based on your previously implemented system operations and state machine models;

Submit in team repo.

HW10: Implement GUI within the package structure for the answering machine based on your previously implemented system operations and state machine models;

Submit here.

Evaluations:

• MyCharleston (from the link on “Academic Services” tab)
• Direct web link: coursereview.cofc.edu
• CofC Mobile App: Android |  Apple | Other
• Personalized link that is emailed to students 3 times

Consider Submitting a Poster !!

TP2 Deliverable 8 Revised: Improve upon D8;

Submit in team repo.

T 17 Apr

Presentations:

TP2 Deliverable: Presentation;

Submit in team repo.

Presentations:

W 25 Apr

S 28 Apr

Final

FINAL 8am - 11am

Final grades noon 7 May.